Skip to content

feat: add @salesforce/lightning-dev as JIT plugin @W-21188143@#2608

Open
wjhsf wants to merge 3 commits intosalesforcecli:mainfrom
wjhsf:wjh/jit-lightning-dev
Open

feat: add @salesforce/lightning-dev as JIT plugin @W-21188143@#2608
wjhsf wants to merge 3 commits intosalesforcecli:mainfrom
wjhsf:wjh/jit-lightning-dev

Conversation

@wjhsf
Copy link

@wjhsf wjhsf commented Feb 24, 2026

What does this PR do?

This PR adds @salesforce/lightning-dev to the CLI as a JIT plugin.

Testing Notes

What testing is required for this kind of change?

Checklist

  • This change has been approved by the CLI Review Board or approval isn't required. Anything that adds/changes/deletes commands, flags, output, or json output has to be reviewed.
  • Does this follow the deprecation policy?

What issues does this PR fix or reference?

W-21188143

@wjhsf wjhsf changed the title feat: add @salesforce/lightning-dev as JIT plugin feat: add @salesforce/lightning-dev as JIT plugin @W-21188143@ Feb 24, 2026
"@salesforce/plugin-dev": "2.5.1",
"@salesforce/plugin-devops-center": "1.2.27",
"@salesforce/plugin-flow": "1.0.5",
"@salesforce/plugin-lightning-dev": "6.2.15",
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This corresponds to the next dist tag on npm. Is that the correct version to use?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good call out. This will cause issues. The script that we use to find and bump the latest versions of these JIT plugins (every time the CLI releases) will first look for a latest-rc dist tag and then it will fall back to lastest. (source)

The version you want to include as a JIT dep will need to be published to npm as either latest-rc or lastest

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants